home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19980901-19981211
/
000025_news@newsmaster….columbia.edu _Thu Sep 10 13:25:42 1998.msg
< prev
next >
Wrap
Internet Message Format
|
1998-12-10
|
3KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id NAA11279
for <kermit.misc@watsun.cc.columbia.edu>; Thu, 10 Sep 1998 13:25:41 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id NAA26453
for kermit.misc@watsun; Thu, 10 Sep 1998 13:25:40 -0400 (EDT)
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: C-Kermit to MVS upload problems after upgrade to version 6
Date: 10 Sep 1998 17:25:38 GMT
Organization: Columbia University
Lines: 63
Message-ID: <6t922i$5o$1@apakabar.cc.columbia.edu>
References: <35F80436.669@yahoo.com>
NNTP-Posting-Host: watsun.cc.columbia.edu
Xref: news.columbia.edu comp.protocols.kermit.misc:9189
In article <35F80436.669@yahoo.com>, Art L. <art1958@yahoo.com> wrote:
: We have been having problems transfering files between C-Kermit on SCO
: UNIX and Kermit on a IBM 390 mainframe running MVS. We had no problems
: until we upgraded our C-Kermit version from 5.190 to 6.192. The problem
: is that there several retry errors during the transmission. I don't
: have much information on the mainframe version other than it is old. We
: are connected thru a dialup connection via a local GTE Data Services
: phone number. The only kermit settings I was told to use are:
:
: control quote=35
:
This is the default anyway.
: max pack 1024
:
The command for this is SET RECEIVE PACKET-LENGTH 1024.
As noted in the manual, if a particular packet length results in trouble,
then try a shorter one.
: no pad characters
: eol=13
: CRC=1 byte checksum
: Block start =1
:
These are the defaults anyway.
: Packet Length: 1024 1024 Window Size: 3 set, 0 used
:
Nothing suspicious here, except that you have also given the command:
SET WINDOW 3
which you did not mention above. But Kermit-370 does not do sliding
windows. This should cause no harm, since C-Kermit will negotiate down.
But neither does it serve any useful purpose.
: Packet timeouts: dynamic 1:0
:
This is a difference between C-Kermit 5A and 6.0, that might account for
some retries.
: The following is an example of my display after a file upload (I am
: connecting at 14.4K):
:
: Transfer Rate, CPS: 1392
: Error Count: 22
: Last Error: (resend)
:
Well, first off, this is not so bad. 1392 cps on a 1440 cps connection
is pretty good throughput for a half-duplex connection.
However, you should be able to eliminate the retries if C-Kermit 5A did
not get them on exactly the same connection. The most likely culprit is
the new dynamic timeout feature, in which C-Kermit tries to figure out the
packet round-trip time a per-packet basis, rather than using a fixed
timeout. Try giving C-Kermit a command like:
SET SEND TIMEOUT 8 FIXED
This disables the dynamic timeouts and selects a fixed 8-second timeout.
- Frank